Geo-fence valuation system

ABSTRACT

Disclosed, is a geo-fence valuation system to: access usage data at a server system, the usage data collected from a set of client devices located within a geo-fenced area, and wherein the usage data comprises data objects, wherein each data object includes at least a device identifier of a source device of the usage data, and location data; identify one or more data types of the location data, wherein the data types indicate a level of precision of the location data; determine a geodensity of the geo-fenced area based on the usage data, wherein the geodensity indicates at least a number of client devices located within the geo-fenced area; and augments the geodensity of the geo-fence based on the one or more data types of the location data.

TECHNICAL FIELD

Embodiments of the present disclosure relate generally to mobile computing technology and, more particularly, but not by way of limitation, to the valuation of geo-fences for use in the distribution of media content.

BACKGROUND

A geo-fence is a virtual perimeter for a real-world geographic area. For example, by using Radio Frequency Identification (RFID), or Global Positioning Systems (GPS), an area may be marked with a geo-fence using coordinates such as latitude and longitude pairs. Geo-fencing allows an administrator to specify actions that are triggered when a device is detected entering (or exiting) boundaries defined by the geo-fence.

A position or location of a device may be ascertained through various methods that include multilateration of radio signals between cell towers of the networks and the phone, Wi-Fi signals, as well as GPS. Each method of ascertaining the location of the device may have varying degrees of precision. As a result, it is a challenge to determine an accurate count of devices within a geo-fence.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

To easily identify the discussion of any particular element or act, the most significant digit or digits in a reference number refer to the figure number in which that element is first introduced.

FIG. 1 is a block diagram showing an example messaging system for exchanging data (e.g., messages and associated content) over a network in accordance with some embodiments, wherein the messaging system includes a geo-fence valuation system.

FIG. 2 is block diagram illustrating further details regarding a messaging system, according to example embodiments.

FIG. 3 is a schematic diagram illustrating data that may be stored in the database of the messaging server system, according to certain example embodiments.

FIG. 4 is a schematic diagram illustrating a structure of a message, according to some embodiments, generated by a messaging client application for communication.

FIG. 5 is a schematic diagram illustrating an example access-limiting process, in terms of which access to content (e.g., an ephemeral message, and associated multimedia payload of data) or a content collection (e.g., an ephemeral message story) may be time-limited (e.g., made ephemeral) in accordance with some embodiments.

FIG. 6 is a block diagram illustrating various modules of a geo-fence valuation system, according to certain example embodiments.

FIG. 7A is a table depicting various levels of geo-fence precision, according to certain example embodiments.

FIG. 7B is an example of the various levels of geo-fence precision, according to certain example embodiments.

FIG. 8 is a flowchart illustrating various operations of the geo-cell valuation system in determining a geodensity of a geo-fence and augmenting the geodensity based on a data type, according to certain example embodiments.

FIG. 9 is a flowchart illustrating various operations of the geo-fence valuation system in determining a usage density of an event category, according to certain example embodiments.

FIG. 10 is a flowchart illustrating various operations of the geo-fence valuation system in calculating a price-schedule of a geo-fence, according to certain example embodiments.

FIG. 11 is a block diagram illustrating a representative software architecture, which may be used in conjunction with various hardware architectures herein described and used to implement various embodiments.

FIG. 12 is a block diagram illustrating components of a machine, according to some example embodiments, able to read instructions from a machine-readable medium (e.g., a machine-readable storage medium) and perform any one or more of the methodologies discussed herein.

DETAILED DESCRIPTION

Reference will now be made in detail to specific example embodiments for carrying out the inventive subject matter of the present disclosure. In the following description, specific details are set forth in order to provide a thorough understanding of the subject matter. It shall be appreciated that embodiments may be practiced without some or all of these specific details.

Disclosed, is a geo-fence valuation system to determine a geodensity of a geo-fenced area based on a count of unique device identifiers within a geo-fenced area and data types of location data received from client devices within the geo-fenced area. The geo-fence valuation system is configured to access usage data collected from a set of client devices located within a geo-fenced area, wherein the usage data comprises data that include at least a device identifier, an event identifier, and location data indicating a location of the device at the time the usage data was collected. The geo-fence valuation system identifies one or more data types of the location data, wherein the data types indicate a level of precision of the location data, and determines a geodensity of the geo-fenced area based on the usage data. The geodensity indicates at least a number of client devices located within the geo-fenced area; and augments the geodensity of the geo-fence based on the one or more data types of the location data. The data types of the location data include, for example, cell tower data, Wi-Fi data, GPS data, as well as combinations thereof.

In some example embodiments, a geo-cell may be generated based on the location data, wherein the geo-cell indicates a location of a client device to a level of precision based on the data type of the corresponding location data. For example, a data type of high accuracy may have a correspondingly small geo-cell, indicating a high level of precision in determining a location of a client device. The usage data may additionally include user interaction data collected from client devices. For example, the usage data may include media requests to a server system, browser requests, and other similar data types, wherein the data includes location data and temporal data indicating a location and time in which a user of the client device transmitted the data.

In some example embodiments, the geo-fence valuation system determines the geodensity of a geo-fenced area based on a number of unique device identifiers among the usage data collected from the set of client devices. That is to say, the geo-fence valuation system calculates the geodensity based in part on a count of user devices detecting within the boundaries of a particular geo-fence (e.g., a 2 dimensional area or 3 dimensional volume encompassed by the boundaries of the geo-fence). For example, the geo-fence valuation system may access and parse the usage data collected from the set of client devices in order to extract location data depicting the locations of the set of client devices. Based on the location data, the geo-fence valuation system may determine a number of client devices located within the geo-fence.

A geo-cell may be generated based on the location data, wherein the geo-cell indicates a location of a client device to a precision level based on the data type of the location data. For example, the geo-cell may be represented as an enclosed shape (e.g., square, circle) at a location on a map image based on the location data, and dimensions (e.g., an area) based on a data type of the location data. This essentially means that a location of a client device in an area may be determined to level of precision based on the size of the geo-cell. For example, a geo-cell of a high precision level (e.g., GPS data) may identify a location of a client device to a radius of 50 m or less, while a geo-cell of a low precision level (e.g., cellular data, cell tower triangulation data) may only identify the location of the client device within a 500 m radius. Determining an accurate count of a geo-fenced area may therefore prove problematic due to the inherent limitations of location data precision-location data of a low precision level may only specify a location of a device to a very large region that may overlap multiple geo-fenced area, making it difficult to accurately determine a count of a number of client devices actually within the geo-fenced area. For this reason, the geo-fence valuation system determines a geodensity (e.g., a count of client devices within a geo-fenced area), and augments (e.g., increases, decreases) the count based on the data types of the location data received from the client devices.

In some example embodiments, the usage data collected from the client devices may include corresponding event identifiers that identify an event or events occurring at the location encompassed by the geo-fence. For example, the event identifier may include social media check-in data indicating a specific concert, movie, sporting event, party, or the like. In some example embodiments, the event identifier may include “hashtags” generated by users that reference specific events (e.g., concert, movie, sporting event, party). The geo-fence valuation system may determine an event category of the event identified by the event identifier, and calculate a usage density of the event category based on the usage data, where the usage density indicates a number of client devices at the location for the event.

In further embodiments, the geo-fence valuation system is configured to generate a price schedule to distribute content to client devices determined to be at the location encompassed by the geo-fence, based on the usage density of an event category and the geodensity of a geo-fence. For example, the geo-fence valuation system may receive a media distribution request from a client device, wherein the media distribution request includes media content, an event identifier, and a location identifier that identifies a location encompassed by a geo-fence. The geo-fence valuation system accesses historical usage data in response to receiving the media distribution request, and retrieves usage data based on the location identifier and the event identifier of the media distribution request. The geo-fence valuation system may thereby determine a price-schedule of the geo-fenced location based on the usage data, wherein the price-schedule may include a price per number of devices that the media content is delivered to, a price per view of the media content, as well as a period of time in which the media content may be delivered to devices in the location encompassed by the geo-fence.

Consider an illustrative example from a user perspective. A distributor of media content may submit a distribution request to the geo-fence valuation system, wherein the distribution request includes media content, a location identifier, and an event identifier. For example, the location identifier may include GPS coordinates and the event identifier may indicate an event category (e.g., rock concert), or name of an event (e.g., “Woodstock Music Festival”). In response to receiving the distribution request, the geo-fence valuation system accesses a database of historical usage data collected from a set of client devices, and retrieves usage data based on the event identifier and the location identifier. The geo-fence valuation system determines a geodensity of the location identified by the location identifier in the distribution request based on the usage data, and augments the geodensity based on the data types of the location data of the usage data. The geo-fence valuation system may thereby generate a price schedule to deliver media content to devices within the geo-fence based on the augmented geodensity. In some example embodiments, the geo-fence valuation system may generate the price-schedule based on the augmented geodensity and a usage density of the event category associated with the event identifier. The generating of the price schedule may be based on a weighted linear model.

FIG. 1 is a block diagram showing an example messaging system 100 for exchanging data (e.g., messages and associated content) over a network. The messaging system 100 includes multiple client devices 102, each of which hosts a number of applications including a messaging client application 104. Each messaging client application 104 is communicatively coupled to other instances of the messaging client application 104 and a messaging server system 108 via a network 106 (e.g., the Internet).

Accordingly, each messaging client application 104 is able to communicate and exchange data with another messaging client application 104 and with the messaging server system 108 via the network 106. The data exchanged between messaging client applications 104, and between a messaging client application 104 and the messaging server system 108, includes functions (e.g., commands to invoke functions) as well as payload data (e.g., text, audio, video or other multimedia data).

The messaging server system 108 provides server-side functionality via the network 106 to a particular messaging client application 104. While certain functions of the messaging system 100 are described herein as being performed by either a messaging client application 104 or by the messaging server system 108, it will be appreciated that the location of certain functionality either within the messaging client application 104 or the messaging server system 108 is a design choice. For example, it may be technically preferable to initially deploy certain technology and functionality within the messaging server system 108, but to later migrate this technology and functionality to the messaging client application 104 where a client device 102 has a sufficient processing capacity.

The messaging server system 108 supports various services and operations that are provided to the messaging client application 104. Such operations include transmitting data to, receiving data from, and processing data generated by the messaging client application 104. In some embodiments, this data includes, message content, client device information, geolocation information, media annotation and overlays, message content persistence conditions, social network information, and live event information, as examples. In other embodiments, other data is used. Data exchanges within the messaging system 100 are invoked and controlled through functions available via user interfaces (UIs) of the messaging client application 104.

Turning now specifically to the messaging server system 108, an Application Program Interface (API) server 110 is coupled to, and provides a programmatic interface to, an application server 112. The application server 112 is communicatively coupled to a database server(s) 118, which facilitates access to a database(s) 120 in which is stored data associated with messages processed by the application server 112.

Dealing specifically with the Application Program Interface (API) server 110, this server receives and transmits message data (e.g., commands and message payloads) between the client device 102 and the application server 112. Specifically, the Application Program Interface (API) server 110 provides a set of interfaces (e.g., routines and protocols) that can be called or queried by the messaging client application 104 in order to invoke functionality of the application server 112. The Application Program Interface (API) server 110 exposes various functions supported by the application server 112, including account registration, login functionality, the sending of messages, via the application server 112, from a particular messaging client application 104 to another messaging client application 104, the sending of media files (e.g., images or video) from a messaging client application 104 to the messaging server application 114, and for possible access by another messaging client application 104, the setting of a collection of media data (e.g., story), the retrieval of a list of friends of a user of a client device 102, the retrieval of such collections, the retrieval of messages and content, the adding and deletion of friends to a social graph, the location of friends within a social graph, opening and application event (e.g., relating to the messaging client application 104).

The application server 112 hosts a number of applications and subsystems, including a messaging server application 114, an image processing system 116, a social network system 122, and a geo-fence valuation system 124. The messaging server application 114 implements a number of message processing technologies and functions, particularly related to the aggregation and other processing of content (e.g., textual and multimedia content) included in messages received from multiple instances of the messaging client application 104. As will be described in further detail, the text and media content from multiple sources may be aggregated into collections of content (e.g., called stories or galleries). These collections are then made available, by the messaging server application 114, to the messaging client application 104. Other processor and memory intensive processing of data may also be performed server-side by the messaging server application 114, in view of the hardware requirements for such processing.

The application server 112 also includes an image processing system 116 that is dedicated to performing various image processing operations, typically with respect to images or video received within the payload of a message at the messaging server application 114.

The social network system 122 supports various social networking functions services, and makes these functions and services available to the messaging server application 114. To this end, the social network system 122 maintains and accesses an entity graph 304 within the database(s) 120. Examples of functions and services supported by the social network system 122 include the identification of other users of the messaging system 100 with which a particular user has relationships or is “following,” and also the identification of other entities and interests of a particular user. The geo-fence valuation system 124 provides functionality to determine a geodensity of a geo-fence based on usage data collected from a set of client devices.

The application server 112 is communicatively coupled to one or more database server(s) 118, which facilitates access to a database(s) 120 in which is stored data associated with messages processed by the messaging server application 114.

FIG. 2 is block diagram illustrating further details regarding the messaging system 100, according to example embodiments. Specifically, the messaging system 100 is shown to comprise the messaging client application 104 and the application server 112, which in turn embody a number of some subsystems, namely an ephemeral timer system 202, a collection management system 204 and an annotation system 206.

The ephemeral timer system 202 is responsible for enforcing the temporary access to content permitted by the messaging client application 104 and the messaging server application 114. To this end, the ephemeral timer system 202 incorporates a number of timers that, based on duration and display parameters associated with a message, or collection of messages (e.g., a SNAPCHAT story), selectively display and enable access to messages and associated content such as anamorphic media via the messaging client application 104. Further details regarding the operation of the ephemeral timer system 202 are provided below.

The collection management system 204 is responsible for managing collections of media (e.g., collections of text, image video and audio data). In some examples, a collection of media content (e.g., messages, including images, video, text and audio) may be organized into an “event gallery” or an “event story.” Such a collection may be made available for a specified time period, such as the duration of an event to which the content relates. For example, media content such as event specific images and filters may be displayed as a “story” for the duration of that music concert at client devices that enter/transgress a boundary of a geo-fence that encompasses a location of the event. The collection management system 204 may also be responsible for publishing an icon that provides notification of the existence of a particular collection to the user interface of the messaging client application 104.

The collection management system 204 furthermore includes a curation interface 208 that allows a collection manager to manage and curate a particular collection of content. For example, the curation interface 208 enables an event organizer to curate a collection of content relating to a specific event (e.g., delete inappropriate content or redundant messages). Additionally, the collection management system 204 employs machine vision (or image recognition technology) and content rules to automatically curate a content collection. In certain embodiments, compensation may be paid to a user for inclusion of user generated content into a collection. In such cases, the curation interface 208 operates to automatically make payments to such users for the use of their content.

The annotation system 206 provides various functions that enable a user to annotate or otherwise modify or edit media content associated with a message. For example, the annotation system 206 provides functions related to the generation and publishing of media overlays for messages processed by the messaging system 100. The annotation system 206 operatively supplies a media overlay (e.g., a SNAPCHAT filter) to the messaging client application 104 based on a geolocation of the client device 102. In another example, the annotation system 206 operatively supplies a media overlay to the messaging client application 104 based on other information, such as, social network information of the user of the client device 102. A media overlay may include audio and visual content and visual effects. Examples of audio and visual content include pictures, texts, logos, animations, and sound effects. An example of a visual effect includes color overlaying, or projecting an anamorphic media item over a presentation depicting a space. The audio and visual content or the visual effects can be applied to a media content item (e.g., a photo) at the client device 102. For example, the media overlay including text that can be overlaid on top of a photograph or video stream generated taken by the client device 102. In another example, the media overlay includes an identification of a location overlay (e.g., Venice beach), a name of a live event, or a name of a merchant overlay (e.g., Beach Coffee House). In another example, the annotation system 206 uses the geolocation of the client device 102 to identify a media overlay that includes the name of a merchant at the geolocation of the client device 102. The media overlay may include other indicia associated with the merchant. The media overlays may be stored in the database(s) 120 and accessed through the database server(s) 118.

In one example embodiment, the annotation system 206 provides a user-based publication platform that enables users to select a geolocation on a map, and upload content associated with the selected geolocation. The user may also specify circumstances under which a particular media overlay should be offered to other users. The annotation system 206 generates a media overlay that includes the uploaded content and associates the uploaded content with the selected geolocation.

In another example embodiment, the annotation system 206 provides a merchant-based publication platform that enables merchants to select a particular media overlay associated with a geolocation via a bidding process. For example, the annotation system 206 associates the media overlay of a highest bidding merchant with a corresponding geolocation for a predefined amount of time.

FIG. 3 is a schematic diagram 300 illustrating data which may be stored in the database(s) 120 of the messaging server system 108, according to certain example embodiments. While the content of the database(s) 120 is shown to comprise a number of tables, it will be appreciated that the data could be stored in other types of data structures (e.g., as an object-oriented database).

The database(s) 120 includes message data stored within a message table 314. The entity table 302 stores entity data, including an entity graph 304. Entities for which records are maintained within the entity table 302 may include individuals, corporate entities, organizations, objects, places, events etc. Regardless of type, any entity regarding which the messaging server system 108 stores data may be a recognized entity. Each entity is provided with a unique identifier, as well as an entity type identifier (not shown).

The entity graph 304 furthermore stores information regarding relationships and associations between entities. Such relationships may be social, professional (e.g., work at a common corporation or organization) interested-based or activity-based, merely for example.

The database(s) 120 also stores annotation data, in the example form of filters, in an annotation table 312. Filters for which data is stored within the annotation table 312 are associated with and applied to videos (for which data is stored in a video table 310) and/or images (for which data is stored in an image table 308). Filters, in one example, are overlays that are overlaid on an image or video during presentation to a recipient user. For example, the overlay may include media content such as stylized text related to an event or location displayed within a presentation of a space, such that the media content appears to be projected over a set of three dimensional surfaces of a space. Filters may be of varies types, including a user-selected filters from a gallery of filters presented to a sending user by the messaging client application 104 when the sending user is composing a message. Other types of filers include geolocation filters (also known as geo-filters) which may be presented to a sending user based on geographic location. For example, geolocation filters specific to a neighborhood or special location may be presented within a user interface by the messaging client application 104, based on geolocation information determined by a GPS unit of the client device 102. Another type of filer is a data filer, which may be selectively presented to a sending user by the messaging client application 104, based on other inputs or information gathered by the client device 102 during the message creation process. Example of data filters include current temperature at a specific location, a current speed at which a sending user is traveling, battery life for a client device 102 or the current time.

Other annotation data that may be stored within the image table 308 is so-called “lens” data. A “lens” may be a real-time special effect and sound that may be added to an image or a video.

As mentioned above, the video table 310 stores video data which, in one embodiment, is associated with messages for which records are maintained within the message table 314. Similarly, the image table 308 stores image data associated with messages for which message data is stored in the entity table 302. The entity table 302 may associate various annotations from the annotation table 312 with various images and videos stored in the image table 308 and the video table 310.

A story table 306 stores data regarding collections of messages and associated image, video or audio data, which are compiled into a collection (e.g., a SNAPCHAT story or a gallery). The creation of a particular collection may be initiated by a particular user (e.g., each user for which a record is maintained in the entity table 302) A user may create a “personal story” in the form of a collection of content that has been created and sent/broadcast by that user. To this end, the user interface of the messaging client application 104 may include an icon that is user selectable to enable a sending user to add specific content to his or her personal story.

A collection may also constitute a “live story,” which is a collection of content from multiple users that is created manually, automatically or using a combination of manual and automatic techniques. For example, a “live story” may constitute a curated stream of user-submitted content from varies locations and events. Users, whose client devices have location services enabled and are at a common location event at a particular time may, for example, be presented with an option, via a user interface of the messaging client application 104, to contribute content to a particular live story. The live story may be identified to the user by the messaging client application 104, based on his or her location. The end result is a “live story” told from a community perspective.

A further type of content collection is known as a “location story,” which enables a user whose client device 102 is located within a specific geographic location (e.g., on a college or university campus) to contribute to a particular collection. In some embodiments, a contribution to a location story may require a second degree of authentication to verify that the end user belongs to a specific organization or other entity (e.g., is a student on the university campus).

FIG. 4 is a schematic diagram illustrating a structure of a message 400, according to some in some embodiments, generated by a messaging client application 104 for communication to a further messaging client application 104 or the messaging server application 114. The content of a particular message 400 is used to populate the message table 314 stored within the database(s) 120, accessible by the messaging server application 114. Similarly, the content of a message 400 is stored in memory as “in-transit” or “in-flight” data of the client device 102 or the application server 112. The message 400 is shown to include the following components:

-   -   A message identifier 402: a unique identifier that identifies         the message 400.     -   A message text payload 404: text, to be generated by a user via         a user interface of the client device 102 and that is included         in the message 400.     -   A message image payload 406: image data, captured by a camera         component of a client device 102 or retrieved from memory of a         client device 102, and that is included in the message 400.     -   A message video payload 408: video data, captured by a camera         component or retrieved from a memory component of the client         device 102 and that is included in the message 400.     -   A message audio payload 410: audio data, captured by a         microphone or retrieved from the memory component of the client         device 102, and that is included in the message 400.     -   A message annotations 412: annotation data (e.g., filters,         stickers or other enhancements) that represents annotations to         be applied to message image payload 406, message video payload         408, or message audio payload 410 of the message 400.     -   A message duration parameter 414: parameter value indicating, in         seconds, the amount of time for which content of the message         (e.g., the message image payload 406, message video payload 408,         message audio payload 410) is to be presented or made accessible         to a user via the messaging client application 104.     -   A message geolocation parameter 416: geolocation data (e.g.,         latitudinal and longitudinal coordinates) associated with the         content payload of the message. Multiple message geolocation         parameter 416 values may be included in the payload, each of         these parameter values being associated with respect to content         items included in the content (e.g., a specific image into         within the message image payload 406, or a specific video in the         message video payload 408).     -   A message story identifier 418: identifier values identifying         one or more content collections (e.g., “stories”) with which a         particular content item in the message image payload 406 of the         message 400 is associated. For example, multiple images within         the message image payload 406 may each be associated with         multiple content collections using identifier values.     -   A message tag 420: each message 400 may be tagged with multiple         tags, each of which is indicative of the subject matter of         content included in the message payload. For example, where a         particular image included in the message image payload 406         depicts an animal (e.g., a lion), a tag value may be included         within the message tag 420 that is indicative of the relevant         animal. Tag values may be generated manually, based on user         input, or may be automatically generated using, for example,         image recognition.     -   A message sender identifier 422: an identifier (e.g., a         messaging system identifier, email address or device identifier)         indicative of a user of the client device 102 on which the         message 400 was generated and from which the message 400 was         sent     -   A message receiver identifier 424: an identifier (e.g., a         messaging system identifier, email address or device identifier)         indicative of a user of the client device 102 to which the         message 400 is addressed.

The contents (e.g. values) of the various components of message 400 may be pointers to locations in tables within which content data values are stored. For example, an image value in the message image payload 406 may be a pointer to (or address of) a location within an image table 308. Similarly, values within the message video payload 408 may point to data stored within a video table 310, values stored within the message annotations 412 may point to data stored in an annotation table 312, values stored within the message story identifier 418 may point to data stored in a story table 306, and values stored within the message sender identifier 422 and the message receiver identifier 424 may point to user records stored within an entity table 302.

FIG. 5 is a schematic diagram illustrating an access-limiting process 500, in terms of which access to content (e.g., an ephemeral message 502, and associated multimedia payload of data including anamorphic media) or a content collection (e.g., an ephemeral message story 504) may be time-limited (e.g., made ephemeral). For example, an ephemeral message 502 may include an anamorphic media item which may be displayed for a period of time specified by the story timer 514.

An ephemeral message 502 is shown to be associated with a message duration parameter 506, the value of which determines an amount of time that the ephemeral message 502 will be displayed to a receiving user of the ephemeral message 502 by the messaging client application 104. In one embodiment, where the messaging client application 104 is a SNAPCHAT application client, an ephemeral message 502 is viewable by a receiving user for up to a maximum of 10 seconds, depending on the amount of time that the sending user specifies using the message duration parameter 506.

The message duration parameter 506 and the message receiver identifier 424 are shown to be inputs to a message timer 512, which is responsible for determining the amount of time that the ephemeral message 502 is shown to a particular receiving user identified by the message receiver identifier 424. In particular, the ephemeral message 502 will only be shown to the relevant receiving user for a time period determined by the value of the message duration parameter 506. The message timer 512 is shown to provide output to a more generalized ephemeral timer system 202, which is responsible for the overall timing of display of content (e.g., an ephemeral message 502) to a receiving user.

The ephemeral message 502 is shown in FIG. 5 to be included within an ephemeral message story 504 (e.g., a personal SNAPCHAT story, or an event story). The ephemeral message story 504 has an associated story duration parameter 508, a value of which determines a time-duration for which the ephemeral message story 504 is presented and accessible to users of the messaging system 100. The story duration parameter 508, for example, may be the duration of a music concert, where the ephemeral message story 504 is a collection of content pertaining to that concert. Alternatively, a user (either the owning user or a curator user) may specify the value for the story duration parameter 508 when performing the setup and creation of the ephemeral message story 504.

Additionally, each ephemeral message 502 within the ephemeral message story 504 has an associated story participation parameter 510, a value of which determines the duration of time for which the ephemeral message 502 will be accessible within the context of the ephemeral message story 504. Accordingly, a particular ephemeral message story 504 may “expire” and become inaccessible within the context of the ephemeral message story 504, prior to the ephemeral message story 504 itself expiring in terms of the story duration parameter 508. The story duration parameter 508, story participation parameter 510, and message receiver identifier 424 each provide input to a story timer 514, which operationally determines, firstly, whether a particular ephemeral message 502 of the ephemeral message story 504 will be displayed to a particular receiving user and, if so, for how long. Note that the ephemeral message story 504 is also aware of the identity of the particular receiving user as a result of the message receiver identifier 424.

Accordingly, the story timer 514 operationally controls the overall lifespan of an associated ephemeral message story 504, as well as an individual ephemeral message 502 included in the ephemeral message story 504. In one embodiment, each and every ephemeral message 502 within the ephemeral message story 504 remains viewable and accessible for a time-period specified by the story duration parameter 508. In a further embodiment, a certain ephemeral message 502 may expire, within the context of ephemeral message story 504, based on a story participation parameter 510. Note that a message duration parameter 506 may still determine the duration of time for which a particular ephemeral message 502 is displayed to a receiving user, even within the context of the ephemeral message story 504. Accordingly, the message duration parameter 506 determines the duration of time that a particular ephemeral message 502 is displayed to a receiving user, regardless of whether the receiving user is viewing that ephemeral message 502 inside or outside the context of an ephemeral message story 504.

The ephemeral timer system 202 may furthermore operationally remove a particular ephemeral message 502 from the ephemeral message story 504 based on a determination that it has exceeded an associated story participation parameter 510. For example, when a sending user has established a story participation parameter 510 of 24 hours from posting, the ephemeral timer system 202 will remove the relevant ephemeral message 502 from the ephemeral message story 504 after the specified 24 hours. The ephemeral timer system 202 also operates to remove an ephemeral message story 504 either when the story participation parameter 510 for each and every ephemeral message 502 within the ephemeral message story 504 has expired, or when the ephemeral message story 504 itself has expired in terms of the story duration parameter 508.

In certain use cases, a creator of a particular ephemeral message story 504 may specify an indefinite story duration parameter 508. In this case, the expiration of the story participation parameter 510 for the last remaining ephemeral message 502 within the ephemeral message story 504 will determine when the ephemeral message story 504 itself expires. In this case, a new ephemeral message 502, added to the ephemeral message story 504, with a new story participation parameter 510, effectively extends the life of an ephemeral message story 504 to equal the value of the story participation parameter 510.

Responsive to the ephemeral timer system 202 determining that an ephemeral message story 504 has expired (e.g., is no longer accessible), the ephemeral timer system 202 communicates with the messaging system 100 (and, for example, specifically the messaging client application 104 to cause an indicium (e.g., an icon) associated with the relevant ephemeral message story 504 to no longer be displayed within a user interface of the messaging client application 104. Similarly, when the ephemeral timer system 202 determines that the message duration parameter 506 for a particular ephemeral message 502 has expired, the ephemeral timer system 202 causes the messaging client application 104 to no longer display an indicium (e.g., an icon or textual identification) associated with the ephemeral message 502.

FIG. 6 is a block diagram 600 illustrating components of the geo-fence valuation system 124, that configure the geo-fence valuation system 124 to determine a geodensity of a geo-fence that encompasses a location based on usage data collected from a set of client devices, according to various example embodiments. The geo-fence valuation system 124 is shown as including a data retrieval module 602, an identification module 604, a geodensity module 606, and a usage density module 608, all configured to communicate with each other (e.g., via a bus, shared memory, or a switch). Any one or more of these modules may be implemented using one or more processors 610 (e.g., by configuring such one or more processors to perform functions described for that module) and hence may include one or more of the processors 610.

Any one or more of the modules described may be implemented using hardware alone (e.g., one or more of the processors 610 of a machine) or a combination of hardware and software. For example, any module described of the geo-fence valuation system 124 may physically include an arrangement of one or more of the processors 610 (e.g., a subset of or among the one or more processors of the machine) configured to perform the operations described herein for that module. As another example, any module of the engagement tracking system 610 may include software, hardware, or both, that configure an arrangement of one or more processors 610 (e.g., among the one or more processors of the machine) to perform the operations described herein for that module. Accordingly, different modules of the geo-fence valuation system 124 may include and configure different arrangements of such processors 610 or a single arrangement of such processors 610 at different points in time. Moreover, any two or more modules of the geo-fence valuation system 124 may be combined into a single module, and the functions described herein for a single module may be subdivided among multiple modules. Furthermore, according to various example embodiments, modules described herein as being implemented within a single machine, database, or device may be distributed across multiple machines, databases, or devices.

FIG. 7A is a table 700A depicting various levels of data type precision, based on geo-cell radii, according to certain example embodiments. As seen in table 700A, the data types may have five levels of precision ranging from precision level 13 (L13), precision level 14 (L14), precision level 15 (L15), precision level 16 (L16), and precision level 17 (L17). The precision levels of the data types may be based upon the corresponding data types. As seen in table 700A, the data types may include weak cellular data, cellular data, cellular data and Wi-Fi, Wi-Fi and/or poor GPS, and GPS data. Each data type has a corresponding geo-cell dimension and device location radius based on the geo-cell dimension.

For example, as seen in table 7A, a data object from the usage data that includes location data of the GPS data type may indicate a location of a device to within a 50 m radius or less accuracy, wherein the corresponding geo-cell may be approximately 60 m×60 m. Similarly, data objects that includes location data of the cellular data type may indicate a location of a device to within a 250 m radius accuracy, wherein the corresponding geo-cell may be approximately 500 m×500 m.

FIG. 7B is a depiction 700B of the various levels of geo-fence precision, based on dimensions of geo-cells, wherein the dimensions of the geo-cells are based on the corresponding data types, according to certain example embodiments. FIG. 7B includes depictions of a geo-cell 713, a geo-cell 714, a geo-cell 715, a geo-cell 716, and a geo-cell 717, wherein each geo-cell has geo-cell dimensions based on a corresponding data type. For example, geo-cell 713 may correspond to a precision level L13 based on cellular data, while geo-cell 717 may correspond to a precision level L17 based on GPS data.

FIG. 8 is a flowchart illustrating various operations of the geo-cell valuation system 124 in performing a method 800 for determining a geodensity of a geo-fence and augmenting the geodensity based on a data type, according to certain example embodiments. Operations of the method 800 may be performed by the modules described above with respect to FIG. 6. As shown in FIG. 8, the method 800 includes one or more operations 802, 804, 806, and 708.

Operation 802 may be performed by the data retrieval module 602. At operation 802, the data retrieval module 602 accesses a usage data database (e.g., database 120) at a server system, wherein the usage data is collected from a set of client devices located within geo-fenced areas. For example, the geo-fence valuation system 124 receives a distribution request from a client device 102. In this example, the distribution request includes at least a location identifier of a geo-fenced area. In response to receiving the distribution request, the data retrieval module 602 accesses the database 120 to retrieve usage data based on at least the location identifier of the distribution request. For example, the location identifier of the distribution request may specify a specific geo-fence, or geo-fenced area (e.g., “San Jose International Airport, or a specific identifier of a geo-fence known to encompass an area). The usage data may include device identifiers of source devices, location data, temporal data, as well as activity data indicating an activity performed by the client device, such as a media request.

Operation 804 may be performed by the identification module 604. At operation 804, the identification module 604 identifies data types of the location data of the usage data retrieved from the database 120. The data type of the location data indicates a precision of the location data. The data types of the location data may include, for example, cell tower data to determine a location of a mobile device through triangulation, Wi-Fi data, GPS data, as well as combinations thereof.

Operation 806 and 808 may be performed by the geodensity module 606. At operation 806, the geodensity module 606 determines a geodensity of the geo-fence that encompasses the location identified by the location identifier of the distribution request based on a count of unique device identifiers in the usage data.

At operation 808, the geodensity module 606 augments the geodensity based on the data types of the location data. The location data of the usage data may include various data types of varying degrees of accuracy/precision. For example, GPS data may indicate a location of a device to within a geo-cell of a radius of 50 m or less, while weak cellular data may only be able to indicate a location of a device to within a geo-cell of a radius of 500 m. The geodensity module 606 may therefore augment the geodensity of the geo-fence based on the data types of the location data.

In some example embodiments, to augment the geodensity of the geo-fence, the geodensity module 606 disqualifies all data objects from the usage data that include location data with a data type of an accuracy less than that of the most accurate data type precision level. For example, if the most accurate location at among the usage data is GPS data that can indicate a location of a mobile device to within a geo-cell with a radius of 50 m, then the geodensity module 606 may disqualify all less accurate data objects from the usage data. The geodensity module 606 may thereby recalculate the geodensity of the geo-fence based on a number of unique device identifiers among the data objects in the usage data that include location data of the maximum accuracy (i.e., 50 m radius or less).

In some example embodiments, the location data of the data objects that comprise the usage data retrieved by the data retrieval module 602 may include data types of multiple levels of accuracy, as discussed in FIGS. 7A and 7B. For example, the data types may include five levels of accuracy, ranging from: L17 (i.e., 50 m radius or less); L16 (i.e., 60 m radius); L15 (100 m radius); L14 (250 m radius); and L13 (over 500 m radius). To augment the geodensity of the geo-fence, the geodensity module 606 may select data objects from among the usage data that include the L16 level of accuracy, disqualifies the L15, L14, and L13 data types, and splits the L17 data type. The geodensity module 606 may thereby determine the geodensity of the geo-fence based on the number of data objects and/or unique device identifier associated with the L16 data type and half of the number of data objects and/or unique device identifiers associated with the L17 data type.

In further embodiments, to augment the geodensity of the geo-fence, the geodensity module 606 decomposes the data objects that include the L16 data type into a set of (e.g., four) constituent L17 geo-cells located within a single L16 geo-cell. To decompose the data objects, the geodensity module 606 determines a geodensity of the L16 geo-cell, and then distributes the geodensity evenly across four constituent L17 geo-cells that make up the L16 geo-cell.

FIG. 9 is a flowchart illustrating various operations of the geo-fence valuation system 124 in performing a method 900 for determining a usage density of an event category, according to certain example embodiments. The method 900 may be performed as part (e.g., a precursor task, a subroutine, or a portion) of operation 802 of the method 800, according to certain example embodiments.

As seen in operation 802 in FIG. 9, the usage data may comprise data objects that include corresponding event identifiers that identify an event, and wherein the event has a corresponding event category. For example, the event identifier may include a text string (e.g., a “hashtag”) or graphical media included in a message from a client device that indicates an artist's name, and/or an event name (e.g., Iron Maiden concert, Coachella, etc.).

Operation 904 may be performed by the identification module 604. At operation 904, the identification module 604 determines an event category of the event based on the event identifier. For example, the identification module may access a database 120, wherein the database 120 includes a set of event identifiers organized based on event category.

Operation 906 may be performed by the usage density module 608. At operation 808, the usage density module 608 determines a usage density of the event category based on the usage data. For example, the usage density module 608 may determine a unique number of device identifiers among the data objects of the usage data that include the event identifier. Based on the unique number of event identifiers, the usage density module 608 determines a usage density of the corresponding event category, wherein the usage density is an indication of a number of users/client devices that have accessed media content related to the event.

FIG. 10 is a flowchart illustrating various operations of the geo-fence valuation system 124 in performing a method 1000 (for calculating a price-schedule of a geo-fence, according to certain example embodiments. The method 1000 may be performed as part (e.g., a precursor task, a subroutine, or a portion) of operation 802 of the method 800, according to certain example embodiments.

Operation 1002 may be performed by the data retrieval module 602. At operation 1002, the data retrieval module 602 receives a media distribution request from a content distributor (e.g., a client device 102). The media distribution request may include media content, an event identifier, and a location identifier. In some example embodiments, the media distribution request may also include a distribution schedule, wherein the distribution schedule indicates a rate, time period, range, frequency, and volume in which media content is to be distributed.

For example, the media distribution request may indicate that media content (e.g., a filter element) is to be distributed to user devices within a geo-fences area identified by a location identifier, over a period of time (e.g., one hour, one day, one week, etc.), and/or to a total number of devices (e.g., 1,000 devices) or device views.

Operation 1004 may be performed by the identification module 604. At operation 1004, the identification module 604 determines that the event identifier of the media distribution request corresponds to an event of a particular event category, wherein the event category has a corresponding usage density, calculated as discussed above with reference to FIG. 9. The identification module 604 retrieves the corresponding usage density and geodensity based on the media distribution request.

At operation 1006, the geo-fence valuation module 124 calculates a price schedule to distribute the media content within a geo-fence that encompasses a location identified by the location identifier based on the usage density of the event category and the geodensity of the geo-fence. For example, the price schedule may indicate a cost per view of the media content, or a cost per number of devices that receive the media content upon entering the geo-fenced area (e.g., a cost per 1,000 devices that receive the media content). The price schedule may be calculated based on a weighted linear model. The price schedule is communicated to the content distributor so that they may bid on a particular event or location for content distribution.

Software Architecture

FIG. 11 is a block diagram illustrating an example software architecture 1106, which may be used in conjunction with various hardware architectures herein described. FIG. 11 is a non-limiting example of a software architecture and it will be appreciated that many other architectures may be implemented to facilitate the functionality described herein. The software architecture 1106 may execute on hardware such as machine 1100 of FIG. 11 that includes, among other things, processors 1104, memory 1114, and I/O components 1118. A representative hardware layer 1152 is illustrated and can represent, for example, the machine 1100 of FIG. 11. The representative hardware layer 1152 includes a processing unit 1154 having associated executable instructions 1104. Executable instructions 1104 represent the executable instructions of the software architecture 1106, including implementation of the methods, components and so forth described herein. The hardware layer 1152 also includes memory and/or storage modules memory/storage 1156, which also have executable instructions 1104. The hardware layer 1152 may also comprise other hardware 1158.

In the example architecture of FIG. 11, the software architecture 1106 may be conceptualized as a stack of layers where each layer provides particular functionality. For example, the software architecture 1106 may include layers such as an operating system 1102, libraries 1120, applications 1116 and a presentation layer 1114. Operationally, the applications 1116 and/or other components within the layers may invoke application programming interface (API) API calls 1108 through the software stack and receive a response as in response to the API calls 1108. The layers illustrated are representative in nature and not all software architectures have all layers. For example, some mobile or special purpose operating systems may not provide a frameworks/middleware 1118, while others may provide such a layer. Other software architectures may include additional or different layers.

The operating system 1102 may manage hardware resources and provide common services. The operating system 1102 may include, for example, a kernel 1122, services 1124 and drivers 1126. The kernel 1122 may act as an abstraction layer between the hardware and the other software layers. For example, the kernel 1122 may be responsible for memory management, processor management (e.g., scheduling), component management, networking, security settings, and so on. The services 1124 may provide other common services for the other software layers. The drivers 1126 are responsible for controlling or interfacing with the underlying hardware. For instance, the drivers 1126 include display drivers, camera drivers, Bluetooth® drivers, flash memory drivers, serial communication drivers (e.g., Universal Serial Bus (USB) drivers), Wi-Fi® drivers, audio drivers, power management drivers, and so forth depending on the hardware configuration.

The libraries 1120 provide a common infrastructure that is used by the applications 1116 and/or other components and/or layers. The libraries 1120 provide functionality that allows other software components to perform tasks in an easier fashion than to interface directly with the underlying operating system 1102 functionality (e.g., kernel 1122, services 1124 and/or drivers 1126). The libraries 1120 may include system libraries 1144 (e.g., C standard library) that may provide functions such as memory allocation functions, string manipulation functions, mathematical functions, and the like. In addition, the libraries 1120 may include API libraries 1146 such as media libraries (e.g., libraries to support presentation and manipulation of various media format such as MPREG4, H.264, MP3, AAC, AMR, JPG, PNG), graphics libraries (e.g., an OpenGL framework that may be used to render 2D and 3D in a graphic content on a display), database libraries (e.g., SQLite that may provide various relational database functions), web libraries (e.g., WebKit that may provide web browsing functionality), and the like. The libraries 1120 may also include a wide variety of other libraries 1148 to provide many other APIs to the applications 1116 and other software components/modules.

The frameworks/middleware 1118 (also sometimes referred to as middleware) provide a higher-level common infrastructure that may be used by the applications 1116 and/or other software components/modules. For example, the frameworks/middleware 1118 may provide various graphic user interface (GUI) functions, high-level resource management, high-level location services, and so forth. The frameworks/middleware 1118 may provide a broad spectrum of other APIs that may be utilized by the applications 1116 and/or other software components/modules, some of which may be specific to a particular operating system 1102 or platform.

The applications 1116 include built-in applications 1138 and/or third-party applications 1140. Examples of representative built-in applications 1138 may include, but are not limited to, a contacts application, a browser application, a book reader application, a location application, a media application, a messaging application, and/or a game application. Third-party applications 1140 may include an application developed using the ANDROID™ or IOS™ software development kit (SDK) by an entity other than the vendor of the particular platform, and may be mobile software running on a mobile operating system such as IOS™, ANDROID™, WINDOWS® Phone, or other mobile operating systems. The third-party applications 1140 may invoke the API calls 1108 provided by the mobile operating system (such as operating system 1102) to facilitate functionality described herein.

The applications 1116 may use built in operating system functions (e.g., kernel 1122, services 1124 and/or drivers 1126), libraries 1120, and frameworks/middleware 1118 to create user interfaces to interact with users of the system. Alternatively. or additionally, in some systems interactions with a user may occur through a presentation layer, such as presentation layer 1114. In these systems, the application/component “logic” can be separated from the aspects of the application/component that interact with a user.

FIG. 12 is a block diagram illustrating components of a machine 1200, according to some example embodiments, able to read instructions from a machine-readable medium (e.g., a machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, FIG. 12 shows a diagrammatic representation of the machine 1200 in the example form of a computer system, within which instructions 1210 (e.g., software, a program, an application, an applet, an app, or other executable code) for causing the machine 1200 to perform any one or more of the methodologies discussed herein may be executed. As such, the instructions 1210 may be used to implement modules or components described herein. The instructions 1210 transform the general, non-programmed machine 1200 into a particular machine 1200 programmed to carry out the described and illustrated functions in the manner described. In alternative embodiments, the machine 1200 operates as a standalone device or may be coupled (e.g., networked) to other machines. In a networked deployment, the machine 1200 may operate in the capacity of a server machine or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine 1200 may comprise, but not be limited to, a server computer, a client computer, a personal computer (PC), a tablet computer, a laptop computer, a netbook, a set-top box (STB), a personal digital assistant (PDA), an entertainment media system, a cellular telephone, a smart phone, a mobile device, a wearable device (e.g., a smart watch), a smart home device (e.g., a smart appliance), other smart devices, a web appliance, a network router, a network switch, a network bridge, or any machine capable of executing the instructions 1210, sequentially or otherwise, that specify actions to be taken by machine 1200. Further, while only a single machine 1200 is illustrated, the term “machine” shall also be taken to include a collection of machines that individually or jointly execute the instructions 1210 to perform any one or more of the methodologies discussed herein.

The machine 1200 may include processors 1204, memory memory/storage 1206, and I/O components 1218, which may be configured to communicate with each other such as via a bus 1202. The memory/storage 1206 may include a memory 1214, such as a main memory, or other memory storage, and a storage unit 1216, both accessible to the processors 1204 such as via the bus 1202. The storage unit 1216 and memory 1214 store the instructions 1210 embodying any one or more of the methodologies or functions described herein. The instructions 1210 may also reside, completely or partially, within the memory 1214, within the storage unit 1216, within at least one of the processors 1204 (e.g., within the processor's cache memory), or any suitable combination thereof, during execution thereof by the machine 1200. Accordingly, the memory 1214, the storage unit 1216, and the memory of processors 1204 are examples of machine-readable media.

The I/O components 1218 may include a wide variety of components to receive input, provide output, produce output, transmit information, exchange information, capture measurements, and so on. The specific I/O components 1218 that are included in a particular machine 1200 will depend on the type of machine. For example, portable machines such as mobile phones will likely include a touch input device or other such input mechanisms, while a headless server machine will likely not include such a touch input device. It will be appreciated that the I/O components 1218 may include many other components that are not shown in FIG. 12. The I/O components 1218 are grouped according to functionality merely for simplifying the following discussion and the grouping is in no way limiting. In various example embodiments, the I/O components 1218 may include output components 1226 and input components 1228. The output components 1226 may include visual components (e.g., a display such as a plasma display panel (PDP), a light emitting diode (LED) display, a liquid crystal display (LCD), a projector, or a cathode ray tube (CRT)), acoustic components (e.g., speakers), haptic components (e.g., a vibratory motor, resistance mechanisms), other signal generators, and so forth. The input components 1228 may include alphanumeric input components (e.g., a keyboard, a touch screen configured to receive alphanumeric input, a photo-optical keyboard, or other alphanumeric input components), point based input components (e.g., a mouse, a touchpad, a trackball, a joystick, a motion sensor, or other pointing instrument), tactile input components (e.g., a physical button, a touch screen that provides location and/or force of touches or touch gestures, or other tactile input components), audio input components (e.g., a microphone), and the like.

In further example embodiments, the I/O components 1218 may include biometric components 1230, motion components 1234, environmental environment components 1236, or position components 1238 among a wide array of other components. For example, the biometric components 1230 may include components to detect expressions (e.g., hand expressions, facial expressions, vocal expressions, body gestures, or eye tracking), measure biosignals (e.g., blood pressure, heart rate, body temperature, perspiration, or brain waves), identify a person (e.g., voice identification, retinal identification, facial identification, fingerprint identification, or electroencephalogram based identification), and the like. The motion components 1234 may include acceleration sensor components (e.g., accelerometer), gravitation sensor components, rotation sensor components (e.g., gyroscope), and so forth. The environment components 1236 may include, for example, illumination sensor components (e.g., photometer), temperature sensor components (e.g., one or more thermometer that detect ambient temperature), humidity sensor components, pressure sensor components (e.g., barometer), acoustic sensor components (e.g., one or more microphones that detect background noise), proximity sensor components (e.g., infrared sensors that detect nearby objects), gas sensors (e.g., gas detection sensors to detection concentrations of hazardous gases for safety or to measure pollutants in the atmosphere), or other components that may provide indications, measurements, or signals corresponding to a surrounding physical environment. The position components 1238 may include location sensor components (e.g., a Global Position system (GPS) receiver component), altitude sensor components (e.g., altimeters or barometers that detect air pressure from which altitude may be derived), orientation sensor components (e.g., magnetometers), and the like.

Communication may be implemented using a wide variety of technologies. The I/O components 1218 may include communication components 1240 operable to couple the machine 1200 to a network 1232 or devices 1220 via coupling 1222 and coupling 1224 respectively. For example, the communication components 1240 may include a network interface component or other suitable device to interface with the network 1232. In further examples, communication components 1240 may include wired communication components, wireless communication components, cellular communication components, Near Field Communication (NFC) components, Bluetooth) components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components to provide communication via other modalities. The devices 1220 may be another machine or any of a wide variety of peripheral devices (e.g., a peripheral device coupled via a Universal Serial Bus (USB)).

Moreover, the communication components 1240 may detect identifiers or include components operable to detect identifiers. For example, the communication components 1240 may include Radio Frequency Identification (RFID) tag reader components, NFC smart tag detection components, optical reader components (e.g., an optical sensor to detect one-dimensional bar codes such as Universal Product Code (UPC) bar code, multi-dimensional bar codes such as Quick Response (QR) code, Aztec code, Data Matrix, Dataglyph, MaxiCode, PDF417, Ultra Code, UCC RSS-2D bar code, and other optical codes), or acoustic detection components (e.g., microphones to identify tagged audio signals). In addition, a variety of information may be derived via the communication components 1240, such as, location via Internet Protocol (IP) geo-location, location via Wi-Fi® signal triangulation, location via detecting a NFC beacon signal that may indicate a particular location, and so forth.

Glossary

“CARRIER SIGNAL” in this context refers to any intangible medium that is capable of storing, encoding, or carrying instructions for execution by the machine, and includes digital or analog communications signals or other intangible medium to facilitate communication of such instructions. Instructions may be transmitted or received over the network using a transmission medium via a network interface device and using any one of a number of well-known transfer protocols.

“CLIENT DEVICE” in this context refers to any machine that interfaces to a communications network to obtain resources from one or more server systems or other client devices. A client device may be, but is not limited to, a mobile phone, desktop computer, laptop, portable digital assistants (PDAs), smart phones, tablets, ultra books, netbooks, laptops, multi-processor systems, microprocessor-based or programmable consumer electronics, game consoles, set-top boxes, or any other communication device that a user may use to access a network.

“COMMUNICATIONS NETWORK” in this context refers to one or more portions of a network that may be an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), the Internet, a portion of the Internet, a portion of the Public Switched Telephone Network (PSTN), a plain old telephone service (POTS) network, a cellular telephone network, a wireless network, a Wi-Fi® network, another type of network, or a combination of two or more such networks. For example, a network or a portion of a network may include a wireless or cellular network and the coupling may be a Code Division Multiple Access (CDMA) connection, a Global System for Mobile communications (GSM) connection, or other type of cellular or wireless coupling. In this example, the coupling may implement any of a variety of types of data transfer technology, such as Single Carrier Radio Transmission Technology (1×RTT), Evolution-Data Optimized (EVDO) technology. General Packet Radio Service (GPRS) technology, Enhanced Data rates for GSM Evolution (EDGE) technology, third Generation Partnership Project (3GPP) including 3G, fourth generation wireless (4G) networks, Universal Mobile Telecommunications System (UMTS), High Speed Packet Access (HSPA), Worldwide Interoperability for Microwave Access (WiMAX), Long Term Evolution (LTE) standard, others defined by various standard setting organizations, other long range protocols, or other data transfer technology.

“EMPHEMERAL MESSAGE” in this context refers to a message that is accessible for a time-limited duration. An ephemeral message may be a text, an image, a video and the like. The access time for the ephemeral message may be set by the message sender. Alternatively, the access time may be a default setting or a setting specified by the recipient. Regardless of the setting technique, the message is transitory.

“MACHINE-READABLE MEDIUM” in this context refers to a component, device or other tangible media able to store instructions and data temporarily or permanently and may include, but is not be limited to, random-access memory (RAM), read-only memory (ROM), buffer memory, flash memory, optical media, magnetic media, cache memory, other types of storage (e.g., Erasable Programmable Read-Only Memory (EEPROM)) and/or any suitable combination thereof. The term “machine-readable medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, or associated caches and servers) able to store instructions. The term “machine-readable medium” shall also be taken to include any medium, or combination of multiple media, that is capable of storing instructions (e.g., code) for execution by a machine, such that the instructions, when executed by one or more processors of the machine, cause the machine to perform any one or more of the methodologies described herein. Accordingly, a “machine-readable medium” refers to a single storage apparatus or device, as well as “cloud-based” storage systems or storage networks that include multiple storage apparatus or devices. The term “machine-readable medium” excludes signals per se.

“COMPONENT” in this context refers to a device, physical entity or logic having boundaries defined by function or subroutine calls, branch points, application program interfaces (APIs), or other technologies that provide for the partitioning or modularization of particular processing or control functions. Components may be combined via their interfaces with other components to carry out a machine process. A component may be a packaged functional hardware unit designed for use with other components and a part of a program that usually performs a particular function of related functions. Components may constitute either software components (e.g., code embodied on a machine-readable medium) or hardware components. A “hardware component” is a tangible unit capable of performing certain operations and may be configured or arranged in a certain physical manner. In various example embodiments, one or more computer systems (e.g., a standalone computer system, a client computer system, or a server computer system) or one or more hardware components of a computer system (e.g., a processor or a group of processors) may be configured by software (e.g., an application or application portion) as a hardware component that operates to perform certain operations as described herein. A hardware component may also be implemented mechanically, electronically, or any suitable combination thereof. For example, a hardware component may include dedicated circuitry or logic that is permanently configured to perform certain operations. A hardware component may be a special-purpose processor, such as a Field-Programmable Gate Array (FPGA) or an Application Specific Integrated Circuit (ASIC). A hardware component may also include programmable logic or circuitry that is temporarily configured by software to perform certain operations. For example, a hardware component may include software executed by a general-purpose processor or other programmable processor. Once configured by such software, hardware components become specific machines (or specific components of a machine) uniquely tailored to perform the configured functions and are no longer general-purpose processors. It will be appreciated that the decision to implement a hardware component mechanically, in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software) may be driven by cost and time considerations. Accordingly, the phrase “hardware component” (or “hardware-implemented component”) should be understood to encompass a tangible entity, be that an entity that is physically constructed, permanently configured (e.g., hardwired), or temporarily configured (e.g., programmed) to operate in a certain manner or to perform certain operations described herein. Considering embodiments in which hardware components are temporarily configured (e.g., programmed), each of the hardware components need not be configured or instantiated at any one instance in time. For example, where a hardware component comprises a general-purpose processor configured by software to become a special-purpose processor, the general-purpose processor may be configured as respectively different special-purpose processors (e.g., comprising different hardware components) at different times. Software accordingly configures a particular processor or processors, for example, to constitute a particular hardware component at one instance of time and to constitute a different hardware component at a different instance of time. Hardware components can provide information to, and receive information from, other hardware components. Accordingly, the described hardware components may be regarded as being communicatively coupled. Where multiple hardware components exist contemporaneously, communications may be achieved through signal transmission (e.g., over appropriate circuits and buses) between or among two or more of the hardware components. In embodiments in which multiple hardware components are configured or instantiated at different times, communications between such hardware components may be achieved, for example, through the storage and retrieval of information in memory structures to which the multiple hardware components have access. For example, one hardware component may perform an operation and store the output of that operation in a memory device to which it is communicatively coupled. A further hardware component may then, at a later time, access the memory device to retrieve and process the stored output. Hardware components may also initiate communications with input or output devices, and can operate on a resource (e.g., a collection of information). The various operations of example methods described herein may be performed, at least partially, by one or more processors that are temporarily configured (e.g., by software) or permanently configured to perform the relevant operations. Whether temporarily or permanently configured, such processors may constitute processor-implemented components that operate to perform one or more operations or functions described herein. As used herein, “processor-implemented component” refers to a hardware component implemented using one or more processors. Similarly, the methods described herein may be at least partially processor-implemented, with a particular processor or processors being an example of hardware. For example, at least some of the operations of a method may be performed by one or more processors or processor-implemented components. Moreover, the one or more processors may also operate to support performance of the relevant operations in a “cloud computing” environment or as a “software as a service” (SaaS). For example, at least some of the operations may be performed by a group of computers (as examples of machines including processors), with these operations being accessible via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., an Application Program Interface (API)). The performance of certain of the operations may be distributed among the processors, not only residing within a single machine, but deployed across a number of machines. In some example embodiments, the processors or processor-implemented components may be located in a single geographic location (e.g., within a home environment, an office environment, or a server farm). In other example embodiments, the processors or processor-implemented components may be distributed across a number of geographic locations.

“PROCESSOR” in this context refers to any circuit or virtual circuit (a physical circuit emulated by logic executing on an actual processor) that manipulates data values according to control signals (e.g., “commands”, “op codes”, “machine code”, etc.) and which produces corresponding output signals that are applied to operate a machine. A processor may, for example, be a Central Processing Unit (CPU), a Reduced Instruction Set Computing (RISC) processor, a Complex Instruction Set Computing (CISC) processor, a Graphics Processing Unit (GPU), a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Radio-Frequency Integrated Circuit (RFIC) or any combination thereof. A processor may further be a multi-core processor having two or more independent processors (sometimes referred to as “cores”) that may execute instructions contemporaneously.

“TIMESTAMP” in this context refers to a sequence of characters or encoded information identifying when a certain event occurred, for example giving date and time of day, sometimes accurate to a small fraction of a second. 

What is claimed is:
 1. A computer-implemented method comprising: accessing usage data at a server system, the usage data collected from a set of client devices located within a geo-fence, the usage data includes location data that identifies a location encompassed by the geo-fence; identifying a data type of the location data, the data type indicating a precision of the location data; determining a geodensity of the geo-fence based on the usage data, the geodensity indicating a number of client devices within the location encompassed by the geo-fence; and augmenting, by one or more processors, the geodensity of the geo-fence based on the data type of the location data.
 2. The computer-implemented method of claim 1, wherein the usage data includes an event identifier that identifies an event, and the method further comprises: determining an event category of the event based on the event identifier; and determining a usage-density of the event category based on the usage data.
 3. The computer-implemented method of claim 2, wherein the event identifier is a first event identifier, the event is a first event, the event category is a first event category, and the method further comprises: receiving, at the server system, a media distribution request from a content distributor, wherein the media distribution request includes media content, a second event identifier and a location identifier that identifies the location encompassed by the geo-fence; determining the second event identifier corresponds to a second event, wherein the second event is of the first event category; and calculating a price-schedule to distribute the media content within the location identified by the location identifier based on the usage density of the first event category and the geodensity of the geo-fence.
 4. The computer-implemented method of claim 2, wherein the method further comprises: calculating a price-schedule based on the geodensity of the geo-fence and the usage-density of the first event category; and wherein the calculating the price-schedule is based on a weighted linear model.
 5. The computer-implemented method of claim 1, wherein the data type of the location data includes Global Positioning Sensor (GPS) data, cellular data, and Wi-Fi data.
 6. The computer-implemented method of claim 1, wherein the location data comprises multiple data types, and wherein the multiple data types include at least a first data type of a maximum precision, and a second data type of a minimum precision, and wherein the augmenting, by the one or more processors, the geodensity of the geo-fence based on the data type includes: extracting a subset of usage data from the usage data, wherein the subset of usage data includes the second data type; determining the geodensity of the geo-fence based on the usage data that includes the first data type.
 7. The computer-implemented method of claim 1, wherein the location data comprises multiple data types, and wherein the multiple data types include at least a first data type of a maximum precision, and a second data type of a minimum precision, and wherein the augmenting, by the one or more processors, the geodensity of the geo-fence based on the data type includes: extracting a subset of usage data from the usage data, wherein the subset of usage data includes the second data type; splitting the subset of the usage data extracted from the usage data; and determining the geodensity of the geo-fence based on the usage data that includes the first data type and the halved subset of the usage data.
 8. A system comprising: a memory; and at least one hardware processor couple to the memory and comprising instructions that cause the system to perform operations comprising: accessing usage data at a server system, the usage data collected from a set of client devices located within a geo-fence, wherein the usage data includes location data that identifies a location encompassed by the geo-fence; identifying a data type of the location data, the data type indicating a precision of the location data; determining a geodensity of the geo-fence based on the usage data, wherein the geodensity indicates a number of client devices within the location encompassed by the geo-fence; and augmenting, by one or more processors, the geodensity of the geo-fence based on the data type of the location data.
 9. The system of claim 8, wherein the usage data includes an event identifier that identifies an event, further comprising instructions that cause the system to perform operations comprising: determining an event category of the event based on the event identifier; and determining a usage-density of the event category based on the usage data.
 10. The system of claim 9, wherein the event identifier is a first event identifier, the event is a first event, the event category is a first event category, further comprising instructions that cause the system to perform operations further comprising: receiving, at the server system, a media distribution request from a content distributor, wherein the media distribution request includes media content, a second event identifier and a location identifier that identifies the location encompassed by the geo-fence; determining the second event identifier corresponds to a second event, wherein the second event is of the first event category; and calculating a price-schedule to distribute the media content within the location identified by the location identifier based on the usage density of the first event category and the geodensity of the geo-fence.
 11. The system of claim 9, further comprising instructions that cause the system to perform operations further comprising: calculating a price-schedule based on the geodensity of the geo-fence and the usage-density of the first event category; and wherein the calculating the price-schedule is based on a weighted linear model.
 12. The system of claim 8, wherein the data type of the location data includes Global Positioning Sensor (GPS) data, cellular data, and Wi-Fi data.
 13. The system of claim 8, wherein the location data comprises multiple data types, and wherein the multiple data types include at least a first data type of a maximum precision, and a second data type of a minimum precision, and wherein the augmenting, by the one or more processors, the geodensity of the geo-fence based on the data type includes: extracting a subset of usage data from the usage data, wherein the subset of usage data includes the second data type; determining the geodensity of the geo-fence based on the usage data that includes the first data type.
 14. The system of claim 8, wherein the location data comprises multiple data types, and wherein the multiple data types include at least a first data type of a maximum precision, and a second data type of a minimum precision, and wherein the augmenting, by the one or more processors, the geodensity of the geo-fence based on the data type includes: extracting a subset of usage data from the usage data, wherein the subset of usage data includes the second data type; halving the subset of the usage data extracted from the usage data; and determining the geodensity of the geo-fence based on the usage data that includes the first data type and the halved subset of the usage data.
 15. A non-transitory machine-readable storage medium comprising instructions that, when executed by one or more processors of a machine, cause the machine to perform operations including: accessing usage data at a server system, the usage data collected from a set of client devices located within a geo-fence, wherein the usage data includes location data that identifies a location encompassed by the geo-fence; identifying a data type of the location data, the data type indicating a precision of the location data; determining a geodensity of the geo-fence based on the usage data, wherein the geodensity indicates a number of client devices within the location encompassed by the geo-fence; and augmenting, by one or more processors, the geodensity of the geo-fence based on the data type of the location data.
 16. The non-transitory machine-readable storage medium of claim 15, wherein the usage data includes an event identifier that identifies an event, further comprising instructions that cause the machine to perform operations including: determining an event category of the event based on the event identifier; and determining a usage-density of the event category based on the usage data.
 17. The non-transitory machine-readable storage medium of claim 16, wherein the event identifier is a first event identifier, the event is a first event, the event category is a first event category, and further comprising instructions that cause the machine to perform operations including: receiving, at the server system, a media distribution request from a content distributor, wherein the media distribution request includes media content, a second event identifier and a location identifier that identifies the location encompassed by the geo-fence; determining the second event identifier corresponds to a second event, wherein the second event is of the first event category; and calculating a price-schedule to distribute the media content within the location identified by the location identifier based on the usage density of the first event category and the geodensity of the geo-fence.
 18. The non-transitory machine-readable storage medium of claim 16, further comprising instructions that cause the machine to perform operation including: calculating a price-schedule based on the geodensity of the geo-fence and the usage-density of the first event category; and wherein the calculating the price-schedule is based on a weighted linear model.
 19. The non-transitory machine-readable storage medium of claim 15, wherein the data type of the location data includes Global Positioning Sensor (GPS) data, cellular data, and Wi-Fi data.
 20. The non-transitory machine-readable storage medium of claim 15, wherein the location data comprises multiple data types, and wherein the multiple data types include at least a first data type of a maximum precision, and a second data type of a minimum precision, and wherein the augmenting, by the one or more processors, the geodensity of the geo-fence based on the data type includes: extracting a subset of usage data from the usage data, wherein the subset of usage data includes the second data type; determining the geodensity of the geo-fence based on the usage data that includes the first data type. 